@edmaul69
@mitu

Looks like unzipping them was the trick. Also, changing the lower-case .bin to upper-case .BIN was also something I missed. Thank you both for the quick replies and help.

I've encountered this too. Usually just disabling, hitting B (back to apply), and then re-enabling brings it up fine.

@mitu

That is awesome and there are some great new features!

I ended up finding a solution. A fresh image seemed to have solved all the issues. Not entirely sure why, but I think it may have something to do with the way my GPIO pins were set for the Borkin button.

Hate having to start over, but it's nice to be up and operating again!

@gengar103 said in Pi 3 - no HDMI display:

What can be done to get this LCD panel, which worked fine under 3.8.1, to work under 4.3?

Try editing /boot/config.txt and add this hdmi_force_hotplug=1

@mitu I set it up in menu - Start>config controller> hold a to config

@joneill I don't know any other GUI except the Emulationstation frontend.
Are you referring to the RetroPie-Setup text GUI - accesible from the RetroPie system, running RetroPie-Setup ? It's used for configuration/updates/installations, but it's not the default GUI shown when the system boots up, it's only used when needed.

@krokko unless there is a specific reason you need stretch you should be fine with using Jessie. If you for some reason want both OS's, Simple solution would be to have two separate sd cards as they are cheap enough. What is it that you're trying to do/want to do?

@pobs
'I've made sure that none of the other roms are in the .bin format'

What do you mean by this?

You could try replacing the bios file with one downloaded from another source.
You can also try some eboots (ps1 games in a psp compatible format, also known as psx2psp). These are just one file each (.pbp) and should work fine.

@jonnykesh I tried downloading asplashscreen.sh from /splashscreen/ but the file will not download, it says it's "unable to open asplashscreen"

I am doing this with root access on my PC but this is just weird.

@raider2747 That's why the .cue file is needed - its contents describe how the game data/music is distributed in the .bin files. If you open a .cue file (which is nothing but a text file) you'll see that.

@jonnykesh I'll give it a shot with some .n64 files. I'll reply back here once I get a shot to try.

Thanks!

@eralimtv said in RASPBIAN STRETCH LITE:

@mitu Thank you! I will try now. How to upgrade Kodi to the latest version 17.6 on RetroPie image?

Latest available version of Kodi in Raspbian Jessie/RetroPie is 17.4 because 17.5 and 17.6 do not compile anymore on Jessie due to new ffmpeg patches which are not compatible with gcc 4.9.2.
To fix it we need to use a newer version of gcc or make the patches compatible with gcc 4.9.2. Either way is not easy to fix, I will see what I can do.

Regarding quake:

Again I'm an idiot. I never checked to see if the +3 and -3 were the actual values. The axis on a PS4 controller is actually + and - 5. So all I had to do was replace the 3s with 5s. Not sure why binding it to 3 made the controller unresponsive though.

input_remapping_directory = "/opt/retropie/configs/ports/quake/" input_player1_r_y_minus_axis = "+5" input_player1_r_y_plus_axis = "-5" #include "/opt/retropie/configs/all/retroarch.cfg"

@mitu @chipsnblip Hahaha, wow. How embarrassing. Thanks, I will try this and report back.

Here are some tests i have done :

$ jstest /dev/input/js0 Driver version is 2.1.0. Joystick (PowerA Xbox One wired controller) has 6 axes (X, Y, Rx, Ry, Hat0X, Hat0Y) and 13 buttons (BtnX, BtnY, BtnTL, BtnTR, BtnTR2, BtnSelect, BtnStart, BtnMode, BtnThumbL, BtnThumbR, ?, ?, ?). Testing ... (interrupt to exit) Axes: 0: 0 1: 0 2: 0 3: 0 4: 0 5: 0 Buttons: 0:off 1:off 2:off 3:off 4:off 5:off 6:off 7:off 8:off 9:off 10:off 11:off 12:off $ lsmod | grep xpad xpad 18566 0 ff_memless 5315 1 xpad $ evtest /dev/input/event[0] Input driver version is 1.0.1 Input device ID: bus 0x3 vendor 0x24c6 product 0x543a version 0x101 Input device name: "PowerA Xbox One wired controller" Supported events: Event type 0 (EV_SYN) Event type 1 (EV_KEY) Event code 304 (BTN_SOUTH) Event code 305 (BTN_EAST) Event code 307 (BTN_NORTH) Event code 308 (BTN_WEST) Event code 310 (BTN_TL) Event code 311 (BTN_TR) Event code 312 (BTN_TL2) Event code 313 (BTN_TR2) Event code 314 (BTN_SELECT) Event code 315 (BTN_START) Event code 316 (BTN_MODE) Event code 317 (BTN_THUMBL) Event code 318 (BTN_THUMBR) Event type 3 (EV_ABS) Event code 0 (ABS_X) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 1 (ABS_Y) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 3 (ABS_RX) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 4 (ABS_RY) Value 0 Min -32768 Max 32767 Fuzz 16 Flat 128 Event code 16 (ABS_HAT0X) Value 0 Min -1 Max 1 Event code 17 (ABS_HAT0Y) Value 0 Min -1 Max 1 Event type 21 (EV_FF) Event code 80 (FF_RUMBLE) Event code 81 (FF_PERIODIC) Event code 88 (FF_SQUARE) Event code 89 (FF_TRIANGLE) Event code 90 (FF_SINE) Event code 96 (FF_GAIN)

@majestyx okay do this...put the roms into the the colecovision folder NOT the MSX folder. .now make the blueMSX emulator the default (pressing a button right after loading the rom..then the first choice from the list..

after that it will load just fine and simply...

got it

hdmi_mode=82 1080p 60Hz

fixed

I have several joysticks identified as DragonRise Inc. Generic USB Joystick (one of them is completely new). And joysticks identified as Personal Cummunication Systems, Inc. PlayStation Gamepad. None of them has vibration in PSX games (Vibration is enabled in RetroArch menu and in the game; type of the joystick were changed to analog). Should I install some drivers or what (just curious; I can't say, I really need that)?